2013-06-11 - 7626.100 - Spec - Periodically run Credit Re-Org Pgm #FICOSupport
SPECIFICATIONS
7626.100 Spec- Periodically run Credit Re-Org Pgm
Purpose
Investigate and present all options of running the SAP Credit Re-org program by credit controlling area and negative open orders for specific credit accounts.
Admin Info
| Purpose |
Periodically run Credit Re-Org Pgm |
| Requested By |
Joan Profetta |
| Spec Created By |
Sai Valisetti |
| Spec Created Date |
06/14/2013 |
| Spec QA by |
Joan Profetta |
| Objects |
|
| Document Status |
Completed |
References
Prior Tickets
Functional Requirement
Investigate and present all options of running the SAP Credit Re-org program by credit controlling area and negative open orders for specific credit accounts.
SO66
Output for the S066 for the 24251.52
SO67
Net for the Open Deliveries is 0.06-
FD33 shows the same from S066 and S077 which is showing incorrect values as below
If we run the report RVKRED88.... it will simulate and will show the correct result but does not Update the tables.
After correction by the above program check the FD33 values which are coming from SO66,S067
If we run the report RVKRED77 It will correct all the above and will show the corrcet result in S066 and S067
- So need to execute all of the above i.e comparing the S066 and S067 with the report RVKRED88 and execute the report RVKRED77 to corrcet it automatically by the program.**
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
I understood by you that currently are we running this report to eliminate small negative values.
This report can be used not only for the negative values(small-large), zero values(currently in PRD we have 115,369 zero values) and incorrect open sales and open deliveries. Inconsistencies in the open orders and open deliveries can happen because of the rejections with diff rejection reasons codes, returns and combined deliveries , partial, partially billed deliveries, credit memo/debit memo’s or change of credit control area in between.
1. If we delete all the zero values(open sales orders and open deliveries) the performance for reading tables(S066,S057) will increase as every transaction that checks credit limits reads each value including zero’s in the table.
2. Incorrect negative(open sales orders and open deliveries) values can cause wrong values in the credit exposure calculation(credit exposure is calculated by open sales orders and open deliveries and down payments)
3. Incorrect open sales orders and open deliveries cause the incorrect calculation of credit exposure.
4. If the update group (T014-STAFO, Transaction OB45) was changed in a credit control area can cause the incorrect values.
5. Small differences caused (for example 1 cent) due to rounding problems.
Demo: I created a demo in my word document
1. Checked the negative values(S066,S67) for the customer 1007432 and the existing open sales order value is 13548.85.
2. Checked the open sales values in FD32 which is 13548.85.
3. Ran a simulation report RVKRED88 found that sales value supposed to be 35498.01.
4. Ran the report RVKRED77 and changed the negative value to correct values and eliminated zero’s.
5. You can check the back the changed value in FD32 which is 35498.01 and in S066 value is also 35498.01.
Executing this report: is a bit challenging:
For the following reasons the report is no suited for frequent use:
• To ensure an error-free run of RVKRED77, it is necessary to completely block tables VBAK, LIKP and VBRK.As a result, the run of the report is not possible during the current operation.
• Depending on the selection, a program run of RVKRED77 can last a few hours, in extreme cases you may even experience a runtime of a few days.
incorrect.doc
Test Plan
[List test scenarios/cases to be executed here]| Test Scenario |
Expected Results |
|
| 1 |
||
| 2 |
Solution Details
[Provide complete technical details for configuration or programming here]